An ITMS-91061: Missing privacy manifest rejection email looks as follows: ITMS-91061: Missing privacy manifest- Your app includes "<path/to/SDK>", which includes , an SDK that was identified in the documentation as a privacy-impacting third-party SDK. Starting February 12, 2025, if a new app includes a privacy-impacting SDK, or an app update adds a new privacy-impacting SDK, the SDK must include a privacy manifest file. Please contact the provider of the SDK that includes this file to get an updated SDK version with a privacy manifest. For more details about this policy, including a list of SDKs that are required to include signatures and manifests, visit: https://developer.apple.com/support/third-party-SDK-requirements. Glossary ITMS-91061: Missing privacy manifest: An email that includes the name and path of privacy-impacting SDK(s) with no privacy manifest files in your app bundle. For more information, see https://developer.apple.com/support/third-party-SDK-requirements. : The specified privacy-impacting SDK that doesn't include a privacy manifest file. If you are the developer of the rejected app, gather the name of the SDK from the email you received from Apple, then contact the SDK's provider for an updated version that includes a valid privacy manifest. After receiving an updated version of the SDK, verify the SDK includes a valid privacy manifest file at the expected location. For more information, see Adding a privacy manifest to your app or third-party SDK. If your app includes a privacy manifest file, make sure the file only describes the privacy practices of your app. Do not add the privacy practices of the SDK to your app's privacy manifest. If the email lists multiple SDKs, repeat the above process for all of them. If you are the developer of an SDK listed in the email, publish an updated version of your SDK that includes a privacy manifest file with valid keys and values. Every privacy-impacting SDK must contain a privacy manifest file that only describes its privacy practices. To learn how to add a valid privacy manifest to your SDK, see the Additional resources section below. Additional resources Privacy manifest files Describing data use in privacy manifests Describing use of required reason API Adding a privacy manifest to your app or third-party SDK TN3182: Adding privacy tracking keys to your privacy manifest TN3183: Adding required reason API entries to your privacy manifest TN3184: Adding data collection details to your privacy manifest TN3181: Debugging an invalid privacy manifest

In this post, we'll share tips to help you submit apps that deliver original ideas to your users. When working on your app, focus on creating interesting, unique experiences that aren't already available. Apps that actively try to copy other apps won't pass review, and accounts that repeatedly submit copycat apps or attempt to impersonate a service will be closed. The rules that prevent copycat and impersonator apps from being distributed on the App Store are described in App Review Guideline 4.1: 4.1 Copycats (a) Come up with your own ideas. We know you have them, so make yours come to life. Don’t simply copy the latest popular app on the App Store, or make some minor changes to another app’s name or UI and pass it off as your own. In addition to risking an intellectual property infringement claim, it makes the App Store harder to navigate and just isn’t fair to your fellow developers. (b) Submitting apps which impersonate other apps or services is considered a violation of the Developer Code of Conduct and may result in removal from the Apple Developer Program. These requirements help make the App Store both a safe place for people to discover apps and a platform for all developers to be successful. Best Practices Here are three best practices that will help you submit apps that follow App Review Guideline 4.1: 1. Submit apps with unique content and features. People want apps that provide unique experiences. Find areas that aren't currently being served and build compelling apps for those audiences. Do: Create apps that provide a new experience or a unique spin on an existing concept. Design original, delightful interfaces that elegantly meet your user's needs. Don't: Don’t imitate the features and functionality of other apps. Don’t copy the look and feel of other apps, such as using an identical user interface design. 2. Make sure App Store metadata only contains relevant information and content you either own or have permission to use. The metadata provided in App Store Connect is used to populate your app's product page on the App Store. People rely on this metadata to learn about your app and what it has to offer. Leveraging the popularity of another brand or app, either by including irrelevant references or protected content, is misleading and won't help your app succeed. Do: Use engaging, descriptive language to describe your unique app. Create original content that best represents your app, such as screenshots showing the actual app in use. Don't: Don't use protected material you do not have the necessary permission to use, such as app icons that are similar to icons of a popular app. Don’t include irrelevant references, such as popular app names or trademarked terms, in any metadata fields. 3. Provide information that is authentic and verifiable. People want to know the developers behind their favorite apps are who they say they are. It's important to continually review and provide up-to-date information, including the developer or company name listed on your Apple Developer Program account, the Support URL listed on your app's product page, and other helpful information. This will enable your users to contact you when they need help and it will also hinder people who may try to impersonate you, your app, or your service. Do: Make sure all information, resources, and documentation related to your account and apps are current and accurate. Don't: Don’t provide inaccurate information or resources, such as directing people to outdated support pages. Don’t provide fraudulent documentation. Accounts that submit fraudulent documentation will be removed from the Apple Developer Program. Support Incorporating these best practices into your app's development will help you submit apps that follow App Review Guideline 4.1. If you need additional assistance, consider taking advantage of one of the following support options available from App Review: If your submission has been rejected, reply to the message from App Review in App Store Connect and request clarification. Request an App Review Appointment to discuss the results of our review. Appointments are subject to availability, and take place during local business hours in your region on Tuesdays and Thursdays. If you believe your app follows the App Review Guidelines, consider submitting an appeal to the App Review Board. Resources Learn about foundational design principles from Apple designers and the developer community. Learn how to create engaging App Store product pages. Note that apps that violate intellectual property rights are subject to removal through the App Store Content Dispute process. If you believe an app on the App Store violates your intellectual property rights, you can submit a claim.

This is my first launch, and i submitted 4 versions of my app. All the versions were reviewed and accepted. For each submission i filled in the Age Rating questionnaire, but after all the 7 steps, it shows UnRated. When i fill in the questions for the Age Rating, and in my game app i have no nudity/obscene or defamatry content of any sort, and i eplxicitly mark this questions to NONE, but after answering all questions, on the final step i see the warning: "Based on your selections, this app can't be made available on the App Store. Apps on the App Store can’t contain any obscene, pornographic, offensive or defamatory content or materials of any kind (text, graphics, images, photographs, and so on)." Which is BS because the app contains nothing of the sort and epxlicitly answered all related questions that it contains nothing of the sort and the app submissions are reviewed and accepted for distribution,.

Our app has been in review for 7 days with no updates. We’ve followed up by email, phone, and even submitted an expedited request, but haven’t heard back. Can someone clarify why it’s stuck and what we can do to move it forward?

Hi there, My app update submission was stuck in "Waiting for Review" state for over 80 hours. Yesterday I canceled and resubmitted it again after 3.5 days of inactivity, but this time it still hasn’t moved forward. I'd like to be sure that there is no issues on my side during sending build to review, cuz I noticed that submit app flow was slightly changed a week ago. Usually app update was verified in 10-20 hours, but now it's stuck. Thank you in advance.

Hello, Our auto-renewable subscription products are currently showing as “In Review” in App Store Connect. However, they are not visible in the “In-App Purchases” section of the app version submission, so we cannot confirm or re-attach them to this app version. At the same time, we cannot delete or edit these products while they are in this state. This has left us in a situation where: The IAPs are stuck in “In Review” status, We cannot re-submit or re-attach them, And your review team cannot complete testing because the subscriptions are not yet approved. According to Apple’s own documentation, IAPs that are released with an app version only move from In Review to Approved when the app itself is approved. This means they must be reviewed together. Could you please: Confirm that our IAPs are correctly attached to this app version and will be reviewed together, or Reset their status back to “Ready to Submit” so that we can re-attach them properly to this app version? We want to make sure we are not stuck in a loop where the IAPs cannot be approved until the app is approved, but the app cannot be approved because the IAPs are stuck. Thank you for your help in resolving this situation. Best regards,

Lately every app that I submit (games) with in app purchases, always coins , the app gets rejected with: Guideline 3.1.1 - Business - Payments - In-App Purchase Your app uses intermediary currency to purchase items that function as non-consumable products but still does not include a restore mechanism. Users restore transactions to maintain access to content that they've already purchased It baffles me that reviewers think buy different number of coins is non-consumable. I have tried to explain that coins will be used to buy weapons and skins and they will also be earned at the end of every level yet for some reasons they are still rejecting the app. It is absurd. This is the second app that I have to go through with this. The first one they eventually figured it out but this one no.

Hello, Our app gets rejected for the reason that the reviewer cannot purchase the subscription with the message, "Guideline 2.1 - Performance - App Completeness We found that your in-app purchase products exhibited one or more bugs which create a poor user experience. Specifically, we were unable to purchase Auto-Renewable Subscriptions. The app launched back to the rendering when we tap on the "Get started"" When we test this with our sandbox accounts in test flight version, we can see the subscribe pop up showing and purchase successfully. But turns out they cannot. Unfortunately we cannot see the reason why and even after requesting further explanation regarding how to move along, we are not getting any explanations. Our subscription products are submitted in the first time with the app and they are in "In review" state for more than a week. We requested phone calls and wrote messages to reviewers many times but unfortunately there's no help yet.

I built the Appvector tool – aso.report, a completely free ASO analysis platform designed to help indie developers easily improve their App Store listings without complex metrics or costly subscriptions. Just paste your app’s URL to get instant insights, multi-country analysis, and actionable recommendations - making ASO simple, accessible, and effective for everyone.

Hello everyone, My app was recently rejected under Guideline 4.1 – Design: Copycats. The review team mentioned that my app or its metadata appears to be misrepresenting itself as another popular app or service, and therefore was not approved. This came as a surprise, because my app is an original trading journal product that I’ve built from scratch. While there are other trading journals in the market, my app has unique features and a different design. I did not intend to copy or impersonate any existing app. I would really appreciate advice from anyone who has gone through a similar rejection: What kind of changes did you make to get past this rejection? Should I focus more on branding (name, logo, color scheme) to differentiate? Is it helpful to write an explanation to the App Review team describing how my app is unique? Any tips or experiences would be very helpful, since I want to make sure my app stands out clearly and avoids any resemblance issues. Thank you in advance!

Since the app was submitted on September 11, it has been stuck in the "in review" status for more than 3 days without being rejected, without further information updates, and without any other feedback. We can't delay any longer, the lack of progress is disrupting our plans. Please inform us immediately on how to proceed or upgrade the review. We contact the Apple review team almost every day (via email), but there is no clear reason for the response. This makes us feel frustrated while waiting for feedback, and at the same time, our users cannot wait any longer. Any help would be greatly appreciated! Thanks.

ASO is by far one of the most frustrating parts of being an indie iOS dev. Despite trying keywords, descriptions, screenshots, and icons, results are unpredictable and competing with big-budget apps feels impossible. Has anyone found a way to make it work?

Since the app was submitted on September 3, it has been stuck in the "in review" status for more than 7 days without being rejected, without further information updates, and without any other feedback. We can't delay any longer, the lack of progress is disrupting our plans. Please inform us immediately on how to proceed or upgrade the review. We contact the Apple review team almost every day (via email), but there is no clear reason for the response. This makes us feel frustrated while waiting for feedback, and at the same time, our users cannot wait any longer.

Hi everyone, Our app has been stuck in "Waiting for Review" status for 2 days now and we’re starting to get very concerned. Details: Version 7.0.4 All required metadata completed It usually takes less than a day for the reviews to be done but it is now two days and we do not want to abuse the expedited review policy. It seems unusually long considering that the typical review time is just a day or less. Has anyone else run into similar delays lately? Is there any other way to escalate the issue or get Apple’s attention other than an expedited review? Thanks in advance for any help or advice!

Did you got a similar letter ? " This letter serves as notice of termination of the Apple Developer Program License Agreement ...Pursuant to Section 3.2(f) of the ADP Agreement.." Fast forward, we are a corporation that spend over 1M on development for our app at apple store. Out of the blue we got this letter and our app was removed within the same day. No warning email prior, No appeal option afterwards. We were banned for a year. We tried to get at least a reply what we did wrong? So far no explanation. We suspect this is either: A campaign from our competitors, trashing our app with tons of neg/positive reviews. (If so, Why is so easy, for bad actors to manipulate Apple Algorithms and to destroy legit apps and why Apple allows it) ? Either someone else complained about our name or logo. (If so, Apple should ask for document, because we hold trademarks of our logos and names). Section 3.2(f) is very murky without clear language. Up to this day we don't know why our business was destroyed in 1 day ! As consequence of our ban, We are loosing legit advertisers like banks, and brands. We are looking forward for our day in court ! Discovery process will solve the mystery of our ban. The most scariest part of our situation, that might be your situation tomorrow, is the uncertainly in the future, that some bot might flag your app for removal and all your time and investment is gone within a day, without any explanation, and without the possibility to speak to a human. Millions of developers are paying $100 per year. This kind of money should be enough to pay at least, for human customer service, to serve the developers community properly. Did this happen to you too ?

Hi everyone, Our game has been stuck in "Waiting for Review" status for 2 days now and we’re starting to get very concerned. Details: Game category: Games/Puzzles Version 1.0 All required metadata completed Age rating: 4+ We’ve tried the following steps multiple times: Removed and re-submitted the build four times to draw attention to the submission Submitted an expedited review request (no response or movement) It seems unusually long considering that the typical review time is just a few days. Has anyone else run into similar delays lately? Is there any other way to escalate the issue or get Apple’s attention? Thanks in advance for any help or advice!

I'm looking to learn from others in the community. Please share any effective tips, hacks, or approaches you've used to boost app visibility and downloads through App Store SEO. Insights on keywords, descriptions, or metadata optimization are especially welcome.

Hi, I'm here hoping for some help or advice in terms of a critical situation I'm currently facing. I've submitted an iOS app more than one month ago, it was quickly got review and rejected twice, and when I re-submit the third time with new build, it then was stuck in the "Waiting for review" status for about 3 weeks. Then, I decided to withdraw the submission and re-submit again, but it doesn't work and remain "Waiting for review" status until now. During these waiting period, I’ve contacted Apple Support multiple times through mails, and received confirmation that my expedited review request was approved. However, no progress has been made since then. Here is a quick summary of the timeline Initial submission: July 29, 2025 Rejected due to Guideline 4.2.2 & 2.1: July 30, 2025 Second submission: Aug 4, 2025 Rejected due to Guideline 4.2.2 & 4.2.0: Aug 6, 2025 Third submission: Aug 6, 2025 Withdraw third & create forth submission: Aug 25, 2025 If anyone from the App Review team sees this post, or if any developers have experienced a similar situation and can offer advice, we would be truly grateful. Thank you in advance for your time and support.

When attempting to submit our application for review, I encountered an error message that does not specify the actual cause of the failure. Since the error message provides no indication of the underlying issue, I am unable to identify what is preventing the submission. Could you please advise what should be done? Noting that all app information is accurrate and filled and this is the first time I face such an issue.

We have a React Native iOS app where we are planning to adopt a micro-frontend architecture using Re.Pack. Some modules of the app would be hosted on a CDN and loaded on demand at runtime instead of being bundled fully inside the app. Is this approach compliant with Apple’s App Store Review Guidelines? Specifically, would loading JavaScript bundles or features dynamically from a CDN (instead of shipping all modules within the app binary) be acceptable for App Store approval? If there are any restrictions or best practices we should follow for this type of setup, please advise.

I have ceated a new version, and the status of it is "Prepare for submission", is there a way to delete it, kindly check the attached image.

Hello, PrivacyInfo.xcprivacy Is primordial and without it the app is rejected from the Store I believe. All 5 ressources I had found related to it, mention XCODE, or explain how to add the code to langages that I don't use (Switf i think?) etc. I am building the app thought CI/CD, so prior to building it the app does not have privacy manifest and there is not way to generate it automatically without xcode it seems. My app is written in Flutter prior to becoming an iOS app. I am seeking for a method to do that. Thanks.